Runtimes within an environment

There are important limitations on attaching runtimes to environments.

tip

High-Scale Environments: For environments running a large number of Integration Packs, the recommended setup sequence is to attach all planned runtimes before installing integration packs. When adding a runtime to an environment that already has many Integration Packs, do so one at a time and during off-peak hours for the smoothest experience. Contact your Boomi representative or Partner Success team if you want guidance on runtime attachment sequencing for large-scale environments.

Attaching runtimes to environments is controlled on the Environments page. The Unattached Runtimes list shows all runtimes that are not attached to any environment.

• For accounts with Basic environment support, each environment in the account can have a single runtime attached.

• For accounts with Unlimited environment support, each environment can have an unlimited number of runtimes attached.

If your account has Unlimited environment support and test connections are enabled, you can attach local basic runtimes to production or test environments. A runtime cloud can be attached only to an environment with the same classification. In other words, test runtime clouds can only be attached to test environments, and production runtime clouds can only be attached to production environments. If you set up additional cloud attachments in a runtime cloud, those cloud attachments can be attached only to an environment with the same classification.

When you attach a runtime to an environment, connection licenses are calculated based on the environment classification:

• Attaching a runtime to a test environment recalculates the test connection licenses.
• Moving a runtime from one environment classification to another recalculates the connection licenses.
• Detaching a runtime from a test environment and attaching it to a production environment recalculates both the test and production connection licenses.

Refer to the Test connection licensing topic for more information.

Deployed processes to which an environment are already attached can execute in runtimes subsequently attached to that environment upon attachment. Execution occurs automatically for those processes for which a default schedule is enabled.

Attaching or detaching a runtime

You can attach or detach runtimes using the Manage > Runtime Management page. For accounts with Basic environment support, each environment in the account can have a single runtime attached. For accounts with Unlimited environment support, each environment can have an unlimited number of runtimes attached.

note

You must have the Runtime Management, Environment Management, and Packaged Component Deployment privileges to perform this task. If you have the Runtime Management Read Access privilege, you cannot perform the task.

When you add a runtime to an existing environment, all encrypted values must be re-entered in the Environment Extensions dialog after the runtime is added.

1. Go to Manage > Runtime Management.

2. To attach a runtime, do one of the following:

   a. Click an environment in the Environments list on the left.

   Under Configuration, click in the Attachments field and select a runtime from the list.

   b. In the Environments list on the left, click an unattached runtime.

   From Attach to Environment, select an environment from the drop-down list.

   c. In the Environments list on the left, drag a runtime from the Unattached runtimes list to the environment that you want to attach it to, and click OK.

3. To detach a runtime, do one of the following:

   a. Click an environment in the Environments list on the left.

   Under Configuration, clear the check box next to the runtime name in the Attachments list, and then click OK.

   b. In the Environments list on the left, click an attached runtime.

   From the Runtime Controls section of the Runtime Information panel, click Detach From Environment, and then click OK.